docs: Start defining the owners of code sections
authorEmmanuele Bassi <ebassi@gnome.org>
Mon, 16 Apr 2018 08:41:24 +0000 (09:41 +0100)
committerEmmanuele Bassi <ebassi@gnome.org>
Mon, 16 Apr 2018 15:06:33 +0000 (16:06 +0100)
commit0b4bfd5c935a1a35893dfb71c4044fded4ba9100
tree5119d3b9ab404223e56007bc13440b25424db3c3
parentd79f1fdbce094ca38adff24bd8c3bbd6ee268503
docs: Start defining the owners of code sections

When filing a new merge request it's often hard to know who to ask for a
review; using the Git log doesn't always help — the person that touched
a file last may just be fixing the build or a compiler warning.

The `CODE-OWNERS` file format is something that GitHub uses in order to
pre-fill the list of reviewers:

  https://help.github.com/articles/about-codeowners/

Ideally, in the future, we'll be able to use this file with a bot like
homu to automatically go through newly filed merge requests and
automatically ask the relevant people for reviews, instead of doing this
manually.
CONTRIBUTING.md
docs/CODE-OWNERS [new file with mode: 0644]